Mobile device and server for task assignments and pickup requests

ABSTRACT

Mobile device for communicating arrival information at a waypoint, communicating that information to a server, receiving a set of tasks (statically assigned or dynamically assigned) for the user (for example, from the server or from another user), displaying the set of tasks to the user, receiving a completion response (successful or unsuccessful) from the user, and proceeding to the next waypoint along a route/trip plan. A coordination server facilitates communication of a list of tasks assigned to a user to be performed at a specified location. The list of tasks is delivered to the user of the first mobile device by the coordination server (if such tasks exist) when the coordination server receives notification from the first mobile device indicating arrival at a specific location.

CROSS REFERENCES TO RELATED APPLICATIONS

The present patent application is a continuation-in-part (CIP) of, claims priority to, and makes reference to U.S. non-provisional patent Ser. No. 14/136,655, filed Dec. 20, 2013, entitled “MOBILE DEVICE AND SERVER FOR GPS SERVICES BASED TASK ASSIGNMENTS”, which in turn is a continuation of, claims priority to, and makes reference to U.S. non-provisional patent Ser. No. 12/070,268, patented as U.S. Pat. No. 8,700,310, issued on Apr. 15, 2014, entitled “MOBILE DEVICE AND SERVER FOR FACILITATING GPS BASED SERVICES”, filed Feb. 15, 2008, which in turn is a continuation-in-part of, claims priority to, and makes reference to U.S. non-provisional patent Ser. No. 12/012,859, patented as U.S. Pat. No. 8,588,814, entitled “CLIENT IN MOBILE DEVICE FOR SENDING AND RECEIVING NAVIGATIONAL COORDINATES AND NOTIFICATIONS”, filed on Feb. 5, 2008. The complete subject matter of all the above-referenced United States Patent Applications is hereby incorporated herein by reference, in their respective entirety.

BACKGROUND

1. Technical Field

The present invention relates generally to a mobile device and particularly to a solution wherein GPS based services are facilitated.

2. Related Art

Mobile devices are becoming ubiquitous. Children carry them and so do adults. Children use them to ask their parents to come pick them up at a mall or a park. Often parents spend a lot of time trying to locate their child at a mall when they get a call for a ride. Similarly, children wait for a long time outside a mall waiting for their parents to arrive, often in inclement weather. This problem is also faced by mobile users who travel to a new country on business and pleasure and wait for a taxi pickup at an airport, outside an airport or in train stations.

Quite often, a user has a mobile phone with a GPS and may desire to go to a store. The user has to type in an address to activate the GPS based navigational facilities. The address could be long and comprise of more than 50 characters quite often, making the user struggle with the painfully small and cramped keyboard on the mobile device. Quite often the keyboards on a mobile device has 3 letters of the alphabet mapped into a single key that makes data entry very complicated and tiring.

Often a user has a mobile phone and drives around town. Unfortunately, the various places the user visits is not known to the user's family or his colleagues at work. If the user's wife had wanted him to buy some stamps when the user was at the post office, she does not have any way to find out if the user visited or went by a post office while driving around town. And the user has no way to automatically determine if his wife needs him to buy something either.

Quite often a manager is a business assigns tasks to his subordinates to get some work done. However, task assignment, such as assigning homes for a sales person to visit on a given day, is usually a priori. If a new task comes up that must be assigned right away, there is no easy way to determine which of the subordinates is the right person to whom the task should be assigned. Such determination may take several phone calls and timely responses from the recipients of those phone calls.

The vCard standard for exchanging electronic business cards has been around for some time and is used for sending email attachments of business cards. They can contain name, address, phone numbers, logos, URLs and photos. However, they do not really help a user in easily navigating from his house to a business (such as a store). There are some deficiencies in the contents of most vCards. Other variations to vCards exists, such as hCard that provide similar features.

GPS satellites have been used for a while for navigation. GPS satellites do not actually pinpoint your location as is commonly believed. The 24 satellites circling the earth each contain a precise clock that transmits a signal comprising a time to the GPS receiver in a user's mobile device. The mobile device processes the satellite signals to determine geometrically where the user is located.

Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of ordinary skill in the art through comparison of such systems with the present invention.

BRIEF SUMMARY OF THE INVENTION

The present invention is directed to apparatus and methods of operation that are further described in the following Brief Description of the Drawings, the Detailed Description of the Invention, and the claims. Other features and advantages of the present invention will become apparent from the following detailed description of the invention made with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective block diagram of a mobile web system wherein a first mobile device with a client software, used by a first user, facilitates sending a location information to a server or to a second mobile device, enabling the server or a client software in the second mobile device to communicate a set of tasks assigned to the first user that are to be completed by the first user after the first user reaches a specific (pre-specified or dynamically specified) location or landmark;

FIG. 2 is an exemplary snapshot of a client feature selection screen of the mobile phone that is presented by the client software that is installed and run in the mobile device in accordance with the present invention;

FIG. 3 is an exemplary screen snapshot of a mobile phone depicting the tasks careen used to review tasks and provide status/responses by a user conducting the tasks; and

FIG. 4 is a flowchart of an exemplary operation of a first mobile device that is capable of receiving tasks assigned to a user when the user with the first mobile device reaches a destination specified where the tasks are expected to be completed by the user.

FIG. 5 is a perspective block diagram of a mobile device with a client software, used by a first user, that facilitates sending a location information to a server or to a second mobile device, and receiving in response a plurality of requests to pickup items, such requests being sent by local businesses and organizations.

DETAILED DESCRIPTION OF THE DRAWINGS

The present invention provides an elegant means of interaction between people wherein the location information from a first user's mobile device is communicated to a second user's mobile device, and to a plurality of other mobile devices, as necessary. The recipients of the location information can act upon it. For example, using the communicated location information, the second user's mobile device guides the second user to the current location of the first user. In addition, the user of the first mobile device can be the recipient for location information communicated by several other users (for example, communicated by other mobile devices). Also, the recipients of the location information can send a task list to the first user's mobile device requesting the first user to complete those tasks.

The present invention facilitates communicating, from a mobile device, arrival information at a waypoint, communicating that information to a server, receiving a set of tasks (statically assigned or dynamically assigned) for the user (for example, from the server or from another user), displaying the set of tasks to the user, receiving a completion response (successful or unsuccessful) from the user, and proceeding to the next waypoint along a route/trip plan.

The present invention makes it possible to map a phone number (of a business or residence, for example) into a corresponding GPS coordinates (such as longitude and latitude). It also makes it possible to dynamically retrieve such mapping information from mobile devices, if necessary, with optional user consent.

FIG. 1 is a perspective block diagram of a mobile web system 101 wherein a first mobile device 121 with a client software 123, used by a first user, facilitates sending a location information to a coordination server 141 or to a second mobile device 161, enabling the coordination server 141 or a client software 163 in the second mobile device to communicate a set of tasks assigned to the first user that are to be completed by the first user after the first user reaches a specific (pre-specified or dynamically specified) location or landmark. For example, a second user specifies what those tasks are that are to be completed by the first user when the first user reaches (arrives at) a desired location. In addition, based on the location information received from the first mobile device 121, the second user, employing the client software 163, communicates the set of tasks that the first user must complete.

The present invention facilitates communicating, from the first mobile device 121, arrival information at a waypoint, communicating that information to the coordination server 141, receiving a set of tasks (statically assigned or dynamically assigned) for the user (for example, from the coordination server 141 or from the second user), displaying the set of tasks to the first user, receiving a completion response (successful or unsuccessful) from the user, and proceeding to the next waypoint along a route/trip plan.

In general, the client software 123 and client software 163 comprise similar functionality and are capable of sending/receiving location information (GPS based, navigational data based, etc.), specifying tasks for another user when the another user reaches a destination associated with the location information, communicating the tasks to the another user on his mobile device when the another user has reached the destination, and receiving a confirmation from the another user that the task is completed (done), skipped or deferred. The another user employs the mobile device that also comprises the client software 123.

In one embodiment, the user of the first mobile device 121 can create tasks and assign them to the second user, employing an entry in a PIM 137 or contact list available in the first mobile device 121 to identify the second user and select him from a list. The user employs the client software 123 for this purpose, wherein the client software 123 employs a task manager module 139 to create/edit/manage the tasks. The tasks can be saved locally and communicated to the second mobile device 161 when the second mobile device 161 (or the second user) sends a notification when approaching a destination or after approaching the destination. The tasks can be also saved remotely at a task database 181 associated with the coordination server 141, and communicated to the second mobile device 161 when the user of the second mobile device 161 sends a notification when approaching a destination or after approaching the destination. At the coordination server 141, the task in the task database 181 is associated with the destination specified, wherein the destination is also stored in a routes and waypoints database 153.

When the first user using the first mobile device 121 is given a ride to his house, such as by the second user, using his vehicle (and perhaps the second mobile device 161 which may be part of the vehicle or separate from it), the second user can save the location coordinates, such as using GPS coordinates, employing the client software 163 available in his GPS enabled second mobile device 161. In particular, the personal information manager (PIM) 177 available in the second mobile device 161 is used by the client software 163 to store the location coordinates, and associate it with the first user's contact information available (or created) in the PIM 177. In one embodiment, the second user is prompted to select one or more PIM 177 entries (contacts in the PIM) and associate the location coordinates with the PIM 177 entries. The updated contact information stored in the PIM 177 comprises GPS coordinates and other navigational data (including optional routes). Such updated contact information can be retrieved in standard formats, such as VCF, and sent as attachments to emails, instant message, etc. When the first user sends an email, and attaches his contact information, such as a contact information in VCF format, the GPS coordinates typically associated with his address (him home address, for example) is sent in the contact information. In one embodiment, the first user's current location coordinates is retrieved using the client software 123 in the first mobile device 121 (dynamically, as and when needed) and incorporated into the contact information in VCF format that is sent as an attachment in an email, etc.

The PIM 137, 177 entries can be stored at a coordination server 141. In one embodiment, users can upload (or enter using a webpage) their own home addresses and business addresses and corresponding GPS coordinates to the coordination server 141.

The coordination server 141 offers a service that, given an address, retrieves GPS coordinates and displays it or communicates it. It also is capable of computing GPS coordinates for a given address. The coordination server 141 is capable of providing a contact information for a given email address based or a given user wherein the contact information also comprises location information such as GPS coordinates for the user. It facilitates retrieving contact information in a VCF format that also incorporates GPS coordinates. The coordination server 141 also offers a service wherein a user can retrieve (from his first mobile device 121, for example) location information for a given phone number or email address. For example, a user can use the phone number of a business and retrieve GPS coordinates for (at least one office/branch/store) the business, or a list of GPS coordinates for one or more locations where the business has a presence. The coordination server 141 also makes it possible to compute geocoding based location information in terms of, for example, latitude and longitude when given an address or a phone number. The present invention makes it possible to map a phone number (of a business or residence, for example) into GPS coordinates (such as longitude and latitude). It also makes it possible to dynamically retrieve that information from the first mobile device 121 if necessary, and with optional first user consent. In a related embodiment, the coordination server 141 maintains a database mapping phone numbers to addresses (and GPS coordinates or is able to compute them from the address) and it provides GPS coordinates and addresses in response to a request by the first user (from the first mobile device 121, for example) wherein the first user provides a phone number as part of the request.

In one embodiment, the client software 123 in the first mobile device 121 communicates a phone number of a business to the coordination server 141 along with the first user's (own user) address or phone number. The coordination server 141 determines a detailed route for traveling from a starting point associated with the first user's phone number (or address) to the destination associated with the business (as determined using the phone number of the business and other related information) and sends details instructions that can be used by the client software 123 in guiding the first user to the destination. Such detailed instructions comprise textual directions, audio directions, maps, places to see and things to do at those locations, or a combination of these.

In one embodiment, the first mobile device 121 does not comprise a GPS circuitry and navigational software. It acquires a current location information, such as GPS coordinates or an address and communicates it to the second mobile device 161, which comprises a GPS circuitry and navigational software. The second mobile device 161 receives the current location information of the first mobile device (such as, directly from the first mobile device 121, from the coordination server 141, etc.) and accepts it, stores in optionally, and navigates to that location.

The user of the first mobile device 121 selects a plurality of addresses using the client software 123 (that browses through the PIM 137 contact lists for example, or other stored set of GPS coordinates) and the client software 123 then determines an optimal route (employing the navigation manager module 129, for example) through those addresses selected. For example, it uses the selected addresses as waypoints and determines an optimal route through them, based on time or distance used as a routing criteria. The client software 123 sends notification to other users along the destination(s) to automatically inform those users of the “approach” and arrival at those destinations(s). In addition, any responses to the notifications sent by the other users from those destination(s), are received by the client software 123 and displayed to the user of the first mobile device 121. The optimal route through those addresses selected by the user can be saved (at the first mobile device 121 and also at the coordination server 141) for subsequent sharing and use. The user can also enter planned/recommended activities for locations associated with those addresses. In addition, the client software can retrieve and incorporate those recommended activities from an external server (for example). The user can optionally download/retrieve tasks assigned to the user for those addresses. The user of the first mobile device 121 can also skip one (or more) of the plurality of addresses identified as destinations along a planned route, using the client software 123. The client software 123 facilitates re-computing of a planned route (or rerouting in general) and enables the user to navigate and travel to the other destinations of interest while skipping the specified ones. In one embodiment, both the notifications sent and responses received are in audio form, although they can be supplemented by textual messages too. In a related embodiment, the coordination server 141 facilitates the sending of notifications by the first mobile device 121 and the receiving of optional responses to those notifications by the first mobile device 121.

The first and second mobile devices 121, 161 are one of a GPS enabled mobile phone, a navigational device (such as a Garmin, TomTom, etc.), a navigational unit in a vehicle (such as a car, motorcycle etc.), a PDA, a laptop with a navigational circuitry/navigational software, etc. They comprise the client software 123, 163 and navigational circuitry, in general.

The coordination server 141 also comprises a task manager 183 that facilitates sending, receiving and storing of tasks by users. In particular, the first user can assign tasks to a second user that need to be completed/attended to when the second user is at a destination (such as a waypoint along a route). In one embodiment, when the first mobile device 121 automatically informs the coordination server 141 (or the second mobile device 161) that it has reached a certain destination, the coordination server 141 distributes tasks assigned to the first user (of the first mobile device 121. For example, the first mobile device 121 may be navigated by the first user, after it has received location information of a destination from webpage or from a route obtained from the coordination server 141 or from the second mobile device 161 (which can be specified as GPS coordinates, landmark information, etc.). The first mobile device 121 guides the user of the first mobile device 121 to that destination. Then the client software 123 of the first mobile device 121 automatically sends a notification with a message comprising the text “Arrived” when it reaches a destination employing the received location information, to the coordination server 141. The coordination server 141 then automatically retrieves tasks if any that are assigned to the first user to be completed (or to be assigned to the first user) on reaching that specific destination. It communicates those tasks (for example, as a list of tasks) to the first mobile device 121 where it is displayed to the user, prompting the user to review them, and execute them if possible. The user is prompted to enter a response after completing those tasks (for example) indicating completion, failure to complete, deferring completion, etc.

The first mobile device 121 comprises the client 123, a processing circuitry 131, a storage 133 and a GPS/navigational circuitry 135. It also comprises the optional PIM 137 (such as a contact list client and database). The client software 123 comprises a GPS management module 125, a navigational coordination module 127, the task manager module 139 and a notification manager module 129. The a GPS management module 125 interacts with the GPS/navigational circuitry 135, retrieving GPS coordinates, setting GPS coordinates for a destination to which the user wants to go, interacting with the navigational coordination module 127, etc. The client software 123 facilitates browsing through the PIM 137, selecting one or more users contact information (comprising an address, GPS coordinates or location information in some format, or even a phone number) to be used as destinations/waypoints, and incorporating their associated locations as waypoints in a planned route (or a route computed). If the PIM 137 entries for any user comprises a phone number, the coordination server 141 is employed to retrieve an associated address and/or GPS coordinates that is then employed for navigating/routing. Thus dynamic routing is possible when the coordination server 141 provides a dynamically determined location information (such as GPS coordinates) for a given phone number (such as a mobile phone number).

The coordination module 127 facilitates setting landmark information where a user desires to go, guiding a user to reach a destination, following a route (according to a trip plan) to reach a destination, retrieving and displaying a computed route, distance and estimated arrival time for reaching a destination, etc. The notification manager module 129 facilitates receiving notification from other mobile devices and displaying them, sending notifications to other mobile devices informing them of a proximity information, approaching information, arrival information, billing information, etc. The second mobile device 161 also comprises modules and circuitry similar to those in functionality that are described here for the first mobile device 121.

The coordination server 141 makes it possible for the first mobile device 121 to interact with one or more other mobile devices, such as the second mobile device 163. It facilitates communication of notifications, GPS coordinates, navigational information such as trip plans, routes, landmarks, distances, approaching and arrival information, etc. It also facilitates billing for trip plans shared with others, trip plans purchased, services accesses such as notification to a waiting user of a first mobile device who needs to know if his ride has arrived, etc.

The coordination server 141 comprises a waypoint and route storage 143, a registration manager 145, a notification coordination module 147, the task manager module 183 and a database 149. The waypoint and route storage 143 stores and retrieves uploaded trip plans, routes, waypoints, bookmarks, etc. A user can upload them for sharing, and optionally bill others for downloading or using them. The registration manager 145 facilitates user registration and service access, wherein user registration comprises creating an account, optionally setting up a billing account, establishing a login and password, and enabling security services. The registration manager 145 makes it possible for users to register the details of their mobile devices such as one or more of a phone number, an IP address, a device serial number such as ESN or IMEI, MSISDN, a subscriber information, etc. It also facilitates registration of phone numbers and other details of friends and family with whom a user's mobile device is likely to share navigational information, receive notifications and requests for navigation data sharing, etc. The notification coordination module 147 facilitates sending notifications and receiving notifications. The coordination server 141 also comprises the task manager 183 that facilitates creation of tasks, assignment of tasks to users, communication of tasks to a user on his mobile device/navigational unit when the coordination server 141 receives a message/communication from the mobile device indicating arrival at a waypoint, and the management of the lifecycle of the tasks and transitions of the states.

The database 149 comprises a contacts and friends list database 151 that makes it possible to specify (and control) who gets to participate in interactions with a registered user, by default. It facilitates mapping (and retrieving) phone numbers to addresses and/or GPS coordinates, for example. It also comprises a routes and waypoints database 153 that is used to store, retrieve and manage waypoints, trip plans and routes uploaded for sharing by users, those that are made available for sale by businesses, etc. The database 149 also comprises an audio and video content database 155 that is used to store, retrieve and manage audio, video, graphic and textual content that a user would enter as user specified data (recorded by the user for example) for a trip plan or waypoint saved and/or shared by the user.

The database 149 also comprises a tasks database 181 that is used to store and retrieve tasks for a plurality of users, wherein the tasks are associated with one or more waypoints. The waypoints are associated with routes assigned to a user or with a trip plan created for/by the user. The user is expected to execute the tasks at the specified waypoints, and report a success or failure information back to the coordination server 141. For example, the user can indicate that a task has been completed, has been deferred or has been skipped. Similarly, the user can indicate if a waypoint along a route has been skipped, in which case any tasks associated with those waypoints are reassigned to other users or deferred until the user reaches those waypoints in a future trip.

The coordination server 141 facilitates communication of a list of tasks assigned to a user to be performed at a specified location. The list of tasks is delivered to the user of the first mobile device 121 by the coordination server (if such tasks exist) when the coordination server 141 receives notification from the first mobile device 121 indicating arrival at a specific location (that may be predetermined as part of a route, or a destination dynamically selected by the user). The client software 123 in the first mobile device 121 displays the list of tasks, and collects confirmation from the user that they were completed (or not). In addition, user inputs for those tasks, in the form of a from data entry, audio inputs, textual data entry, etc. are collected, and stored, and eventually communicated (and sometimes immediately communicated, based on configuration or needs, for example) to the coordination server 141. The list of tasks may be dynamically determined based on one or more criteria, or they may be a predetermined list of tasks identified by the user. In a related embodiment, the tasks are described in audio form that a user of the first mobile device 121 can listen to, and provide feedback to (such as after successful or unsuccessful completion of the task), the feedback being provided in an audio form (voice inputs for example) or in textual form (or as part of a response screen presented to use wherein user checks radio buttons, etc.), etc. In addition, a task assignment module provided by the coordination server 141 facilitates identifying tasks (that are available and presumably not completed) and assigning them to the user, as relevant. These tasks can be identified from a general pool of tasks or from a user-specific pool of tasks (that may have been created by the user himself, for example). Task completions are noted and the pool of tasks are updated, as necessary.

The client software 123 of the first mobile device 121 also comprises a task manager module 137 that facilitates displaying a list of tasks assigned to the user for individual waypoints along a route, prompting the user to provide a task completion response (for example, done, defer, skip), communicating the task completion response to the coordination server 141, etc. It keeps track of skipped and deferred tasks to enable a user to complete them later, if necessary. The coordination server 141 also keeps track of the response received to the tasks so as to be able to reassign some of the plurality of tasks, if necessary, to the same user or to a different user.

FIG. 2 is an exemplary snapshot of a client feature selection 203 screen of the mobile phone 201 that is presented by the client software 123 that is installed and run in the mobile device 201 in accordance with the present invention. The client feature selection 203 comprises the buttons/icons list from 205-227 whose selection will accomplish the corresponding functionality. The various features of the client software can be invoked by a user employing the buttons/icons presented on this screen. This screen has buttons/icons such as ‘Create and Send notification’ 205, a ‘view notification’ 207, a record audio response 209, a capture video/image 211, a messages icon 213, a Download Trips icon 215, an E-mail icon 217, a Contact (PIM) icon 219, an upload trip plan icon 221, a review current tasks icon 223, a Preferences and Settings icon 225, and a review route & waypoints icon 227.

When the user selects the create and send notification button/icon 205 the client software in the mobile device 201 makes it possible for the user to create a new notification from a list of canned notification messages or make a new one. In particular, the client software makes it possible to send the notification to another mobile device. For example, a canned notification comprising the message “About to arrive at destination” is sent to a user of another mobile device to announce the impending arrival at a destination, the location to which had been previously received from the another mobile device.

The view notification icon 207, when activated, invokes screens that facilitate viewing notifications received and notifications sent. In one embodiment, as soon as a notification is received, it is presented to the user in a view notification screen. In addition, a ring, or a jungle is optionally play to bring it to the user's attention. The user can also respond back to the notification, such a response can be provided using audio recording facilities, selecting an appropriate graphic response from a list of pre-created graphics, or by typing text. The record audio response 209 button activates audio functions, such as those that are used to record an audio response, or those used to play audio responses received. In general, a user can choose to provide an audio input to a received notification immediately, or in a deferred/delayed manner, using the record audio response 209 facility.

The capture video/image icon 211 starts video recording, digital photo capture or imaging functionalities. It can also be used to review received video content and play them. The messages icon 213 is used to send messages, for example an SMS message to other mobile phones and client computers. In one embodiment, it is used to send a canned message (pre-recorded) to one or more recipients using the coordination server, wherein the canned message (which may be pre recorded by the user or provided by the service) is either stored and sent from the mobile phone 121 or retrieved from the coordination server 141. In this embodiment, the client 123 is transparently used for sending a message.

The Download trip plans icon 215 supports download of interactive content such as trip plans, from the coordination server, wherein the downloaded content is handled/processed by the client 203 for a service. For example, the trip plans may be tagged with an appropriate MIME type and the client 203 is invoked for content with those MIME types that the client 203 is registered to (and is capable of) handle. In one embodiment, Downloads trip plans 215 provides a shortcut through which a mobile web browser is started and prompts the user to enter a URL of the download site for downloading the trip plan contents.

The e-mail icon 217 starts an e-mail client on the mobile phone prompting the user to login into his e-mail account for sending and receiving e-mails comprising notifications, trip plans, etc. The Contacts icon 219 is the user interface to the ‘PIM’ (personal information management) available in the mobile device 121, 201, which facilitates managing the contact list available in the mobile device 121. The contacts managed in the PIM comprises individual entries for friends/colleagues, etc. and also names of groups of friends, wherein the membership (individual contact information for the members of the group) details are remotely available at the coordination server 141 (or even at an external service provider website, etc.).

The upload trip plan 221 icon facilitates uploading waypoints, trip plans and associated multi-media content, etc. to the coordination server 141. For example, a user is prompted to upload a trip plan that comprises a plurality of routes, each route comprising one or more waypoints and one more associated audio information, video information, pictures, textual descriptions, etc. In addition, each waypoint may one more associated audio information, video information, pictures, textual descriptions. The trip plan is stored as an XML file and uploaded as an XML in one related embodiment. Other forms of structuring, organizing and storing the related data are also contemplated. The trip plan is uploaded to one or more servers, such as the coordination server 141.

The review current tasks icon 223 opens a list of tasks currently assigned to the user that the user can review and provide a status information or response to. The user can review tasks assigned to him as well as task lists created by the user himself. The user can retrieve tasks assigned from the coordination server or those saved locally.

The Preferences and Settings icon 225 facilitates an interface for the configuration of the mobile device 201, 121 in terms of its appearance and performance. The review route & waypoints icon 227 provides a screen where lists of routes are presented, along with lists of waypoints/landmarks/etc. for each route, etc. The user can view tasks assigned (statically) for each waypoint along a route. Later on during navigation, additional dynamically assigned tasks also show up in the list while those reassigned to another user are deleted automatically from the list of tasks displayed.

The client feature selection screen 203 also comprises some soft keys/buttons such as an ‘Option’ soft key 229, a ‘Selection’ soft key 231, and a ‘Back’ 233 soft key. The default action is the ‘Selection’ 231 button on this screen (i.e. the client feature selection screen) of the highlighted icon when the OK button is hit on the ‘joystick’ 245 from the keypad 243.

Activating the 241 key from the keypad 243 will open the Options 229 functionality, which results in presenting the user with a list in a menu or sub-menu, which can be browsed using the ‘joystick’ 245. The ‘Back’ soft key/button 233 will be selected when the key 247 is activated on the keypad 243, to cancel the current screen to go back to the previous one.

FIG. 3 is an exemplary screen snapshot 301 of a mobile phone 121 depicting the tasks careen 303 used to review tasks and provide status/responses by a user conducting the tasks. Such tasks are displayed in lists assembled dynamically by a coordination server and communicated to the mobile device 301, or previously assigned to the user and stored for subsequent access/display.

The tasks screen 303 comprises a current route waypoints 305 list that displays one or more waypoints 307, 309, 311, 313 associated with a current route, sent by the coordination server and dynamically changed (if necessary) by the coordination server or by the user. It also comprises a task list 315 that displays all the tasks associated with a selected waypoint, such as LN postoffice 307, which the user can select from the list 305. The user can select one of the tasks in the list 315 and provide a status information or response indicating completion, etc. For example, using the task actions 381, the user can indicate if a task is done 353, skipped 355 or deferred 357. When the user (and the mobile device) is in proximity to a waypoint destination the tasks for that waypoint/destination is displayed in the task list 315 and the user can try to complete the tasks and provide a response using the buttons in the task actions 381.

The user can add a waypoint to a route using the Add Waypoint pane 323. The user can also skip a waypoint from a route by selecting that waypoint and activating the skip waypoint button 325.

For a selected task in the task list 315, details of the task are displayed in a task details 391 pane/section. In addition, any recorded message can be played using the Play button 335. New tasks can be received dynamically by the mobile device, such as by triggering a receive button 333.

For example, the details of the tasks to be conducted by the first user of the first mobile device after reaching a previously specified destination may have been provided by second user and communicated to the first user navigating to the specified waypoint/destination. The first user would choose one of the tasks at a time, conduct the task, and provide a feedback employing the task actions 381. The first user would review the task details 391 if necessary and even listen to audio or video details for the tasks by activating the play 335 button.

The ‘receive’ button 333 is selected by a user to download all the tasks/messages and notifications that have been received by a user (into his registered user's account, for example). In one embodiment, the received data comprise tasks received, responses for tasks completed, etc. The tasks can be sorted by categories or sorted by date/time on the mobile phone 121 of FIG. 1. In one embodiment, the tasks received are identified by a task name/title.

FIG. 4 is a flowchart of an exemplary operation of a first mobile device that is capable of receiving tasks assigned to a user when the user with the first mobile device reaches a destination specified where the tasks are expected to be completed by the user. The first mobile device comprises a client software capable of navigating to one or more waypoints/landmarks/addresses in a route provided, wherein the waypoints/landmarks information comprise a navigational data such as GPS coordinates.

At a start block 403, the processing starts in the first mobile device when the user starts navigating. Later, at a next block 405, the first mobile device waits for receiving route/trip plans, and displays them. The user may be prompted to accept the route/trip plan (and thereby provide consent). For example, the user of the first mobile device accepts a route/trip plan received and starts following the navigation guidance provided by the first mobile device. In general, waypoint/destination information is provided in the form of a landmark information, a GPS coordinates, etc.

Then, at a next block 407, based on the current route/trip plan, and navigational information thereof, such as GPS coordinates or alternative information (such as a landmark specification), navigation to the next waypoint/landmark is activated. At a next block 409, when the mobile device is at the waypoint/landmark, the user is notified and prompted to conduct the tasks, if any. In one embodiment, the tasks for that waypoint are retrieved from the coordination server by the mobile device after reaching the waypoint/landmark. The coordination server dynamically determines what tasks are to be assigned to the user at that waypoint/landmark. In a different embodiment, the mobile device automatically sends a message/notification to the coordination server on arriving at the destination (waypoint/landmark, etc.) and the coordination server automatically retrieves tasks (from a database or from an external system/computer) and communicates it to the mobile device.

Then, at a next decision block 411, an attempt is made to determine if the user of the first mobile device has any tasks assigned for the current waypoint/landmark/destination. If it is determined that the user does have one or more tasks to be conducted, then, at a next block 413, a determination of the status of completion of the tasks is made, and a report is communicated to the coordination server. For example, the user enters one of the available task actions (such as Done, Skip, Defer) for each of the tasks listed for the user for the current location. Control then passes to the next decision block 415 where an attempt is made to determine if the navigation in accordance with the route/trip plan is completed/done.

If, at the block 415, it is determined that there is no more waypoints/destinations to be visited in accordance with the route/trip plan, then, at a next block 417, a report is sent to the coordination server and the operation exits. Otherwise, the operation proceeds to the next block 407 where navigation proceeds to the next waypoint/landmark, and the user is notified after reaching the that location.

If, at the decision block 411, it is determined that user of the first mobile device does not have any tasks assigned for the current waypoint/landmark/destination, then at the next decision box 415, it is determined if there are no more waypoints/destinations to be visited in accordance with the route/trip plan.

In general, the present invention makes it possible to communicate multimedia contents along with task lists to the mobile device from the coordination server. In addition, routes can be dynamically changed and waypoints added/deleted by the coordination server, such as when a user has reached a waypoint and completes associated tasks, and the coordination server determines that it needs to change tasks at subsequent waypoints, or even to drop or add waypoints. This provides support for ad-hoc modifications to trip plans and routes, and adhoc navigation with consent of users. Such transfer of navigational information (routes being communicated, GPS coordinates being exchanged or waypoint information being exchanged) from the coordination server to the first mobile device is useful and timely. In addition, the combination of GPS coordinate communication with audio message notifications and subsequent responses is convenient for the users involved, with the use of keyboards minimized if not altogether eliminated.

FIG. 5 is a perspective block diagram of a mobile device 509 with a client software 527, used by a first user, that facilitates sending a location information to a server 507 or to a second mobile device 511, and receiving in response a plurality of requests to pickup items, such requests being sent by local businesses and organizations. The mobile device 509 not only receives and displays the items to be picked up 549 based on a current location, a current street name, a current street address or a current destination, but it also receives a task list 549 that the user is expected to work on. In addition, the present invention enables the server 507 or a client software 527 in the second mobile device 511 to communicate a set of tasks assigned to the first user, that are to be completed by the first user, after the first user reaches a specific (pre-specified or dynamically specified) location or landmark, or while the first user is driving along a specific route in proximity.

The present invention discloses the mobile device 509 comprising a global positioning system (GPS) receiver circuitry capable of pinpointing a location and providing directions to a destination. It employs the client software 527 capable of interacting with the GPS receiver circuitry and activating navigation towards the destination. The client software 527 receives a request to navigate to the destination from a second mobile device 511 or the coordination server 507 and accepts the request. It then navigates and provides directions to lead the user to the destination. It also automatically sends notifications to the second mobile device 511. The client software 527 receives tasks and displays them for the user. The present invention also discloses a mobile web system comprising a server 507 communicatively coupled to the first mobile device 509 and the second mobile device 511. The server 507 facilitates sending tasks to the first and second mobile devices 509, 511 after they arrive at a destination of interest. It also facilitates receiving notifications of task completions from a plurality of mobile devices that congregate at a location, and is able to verify their presence, challenge the users for verification/security, etc. The navigational coordinates are based on at least one of a latitude, longitude, and height system, earth centered Cartesian coordinates, earth centered earth fixed, earth centered inertial, and east north up.

The server 507 is communicatively coupled to a mobile device 509 and the server 507 comprises at least one processor for communicating with the mobile device 109, the at least one processor operable to, at least:

-   -   receive a plurality of requests to pick up items, from a         plurality of businesses, along with a corresponding user         identification and addresses of those corresponding businesses         or a reference to those corresponding businesses;     -   receive a current location or a current street name from a         client software in the first mobile device and determine a user         specific set of the plurality of requests to pick up items;     -   deliver to the client software in the first mobile device the         user specific set of the plurality of requests to pick up items;         and     -   deliver an update message, if any are received from the first         mobile device, to the corresponding plurality of businesses.

Thus, the server 507 receives the plurality of requests to pick up items from local businesses, local organizations, etc. and makes it possible to list them using the client software 527 in the mobile device 509. It makes it possible to review them, provide updates, indicate completion, non-completion, deferral, etc. Thus a user, while driving on a route, can automatically get a list of items to pick up, the associated requests having been delivered to the server 507 or to the mobile device 509, directly or indirectly, by local business and organizations. The local businesses and organizations communicate via their own computers, servers 543, websites or mobile devices. The local businesses may alternatively send a pick up request to a social group network used by the user of the mobile device 509, who is a registered customer or a user of associated business services.

In one embodiment, the present invention discloses a mobile device 509 comprising a processing circuitry 571, memory 573 and storage, and a global positioning system (GPS) receiver circuitry. The GPS circuitry not only helps determine a current GPS location (latitude, longitude) but also facilitates navigation to a specific destination or specific destinations. A navigation component 551 facilitates operation and management of the GPS circuitry. A client software 527, that is executed by the processing circuitry 571, comprises the navigation component 551 that interacts with the GPS receiver circuitry. The navigation component 551 is capable of navigating and providing directions to a destination to a user of the mobile device 509. The client software displays a plurality of requests to pick up items received from a plurality of businesses associated with, or located on, a current route being navigated by the navigation component 551. A user of the mobile device 109 selects a route to travel on, and triggers navigation to the various waypoints on the route, for example.

The client software 527 displays a plurality of requests to pick up items received from a plurality of businesses for a user to review, select and act upon. The plurality of businesses are associated with, or located on, a current route being navigated by the navigation component 551. Thus while a user is driving with the mobile device 509 in a vehicle, the notifications or messages sent previously (or actively) by local businesses, that are extracted from a database, that are determined from a list delivered to the mobile device, searched from a todo list available in the client software 527, etc. are displayed for the user, for review and selection. The user can update their status too, as completed, deferred, postponed, etc.

The client software 527 is configured to selectively send a user provided update message regarding the corresponding ones of the plurality of requests to pick up items, to the corresponding plurality of businesses (via their computers, servers or websites).

The client software 527 is configured to selectively send a user provided update message regarding the corresponding ones of the plurality of requests to pick up items, to the corresponding plurality of businesses (via their corresponding servers or computers, etc.). It accepts a task list 549 comprising a plurality of tasks to be completed by the user of the mobile device 109, based on a current location of the mobile device 509, a street name associated with the current location, or based on current route being navigated. The task list 549 comprises various tasks to be conducted by the user of the mobile device 509. The various tasks can be user specific, or generic tasks to be completed by any user while at a specific destination. The tasks in the task list are of various kinds—such as purchasing items from a store or mall, dropping off mail at a post office, dropping off clothes at a laundry, house cleaning, exercising, picking up books at the library, ordering food, making reservations, purchasing tickets for an entertainment show or movie, etc. In some related embodiments, tasks on a task list 549 are also a programming task, a software development task, a design task, a video taping task, a software testing task, a software purchase task, a document preparation task, a design review task, etc. Other types of tasks to be put into the task list are also contemplated.

In one embodiment, the mobile device 509 receives requests to pick up items, such requests being sent by local businesses, friends, or by other organizations. The requests to pick up items comprise requests to pick up one or more of medicines ordered, laundry dropped off, grocery ordered, magazines and books ordered, food ordered, mail stopped, children dropped off, packages awaiting pickup, rental equipment, electronic devices, and equipment dropped off for repairs.

In a related embodiment, the task list 549 comprises a plurality of tasks that are specific to the user, to be completed by the user, after the user has reached the specific destination. The client software in the mobile device is responsible for and capable of managing and reporting the completion status of the plurality of tasks, such as to a coordinating server 507, to a website, to an external business server 543, to an external social group server 541 or to some other mobile system.

In one embodiment, the client software in the mobile device 109 accepts a task list comprising a plurality of tasks to be completed by the user of the mobile device 109, in response to a notification sent by the client software announcing proximity to, or arrival at the destination. In a related embodiment, at each waypoint along a route being followed by a user, the client software sends a notification and receives tasks lists relevant to those specific waypoints, to be completed by the user of the mobile device.

In another embodiment, the client software 109 is configured to convert the plurality of requests to pick up items from a plurality of businesses into a todo list 547 to be presented to the user, wherein the user is also subsequently prompted for completion status update for the items on the todo list 547. In a related embodiment, the todo list 547 is assigned by the user of the mobile device 509 to another mobile user for completion.

The system 505 in one embodiment is a mobile system comprising a plurality of mobile devices 509, 511 including a first mobile device 509 and a second mobile device 511, each of the plurality of mobile devices 509, 511 configured to execute and operate employing a client software 527 capable of sending and receiving GPS based location information, and configured to receive tasks lists for completion by a corresponding user. A coordinating server 507 is communicatively coupled to a plurality of mobile devices 509, 511, and the coordinating server 507 is also configured to receive a plurality of item pickup requests from computers associated with a plurality of businesses for opportunistic distribution to associated ones of the plurality of mobile devices 509, 511. The client software 527 is configured to display the plurality of item pickup requests received from the plurality of businesses associated with, or located on, a current route being navigated by a navigation component of the corresponding one of the plurality of mobile devices 509, 511.

The mobile system of claim 25 allows the first mobile device 509 to send notification to other known and registered users along the optimal route to automatically inform those corresponding registered users of the approach of the first user towards their locations and the subsequent arrival of the first user at those locations. A notification manager 515 in the coordination server 507 facilitates receiving notification from a plurality of mobile devices 509, 511 and forwards them to the first mobile device 509 for display to the user, along with proximity information, approaching information, and arrival information for the plurality of mobile devices.

The coordinating server 507 is configured to receive a plurality of reminders from computers associated with a plurality of businesses, which the coordinating server 507 displays on corresponding ones of the plurality of mobile devices 509, 511 based on their current location, wherein the plurality of reminders are each one of a medical appointment reminder, a vehicle maintenance reminder, a beauty saloon service reminder, a spa service reminder and a fitness center reminder. Thus, the coordinating server gathers reminders and forwards them to the user of the mobile device 509, as and when necessary, based on a current location of the mobile device 509, or the current route of the user using the mobile device 509.

In one related embodiment, the mobile system 505 makes it possible for the client software 527 in the first mobile device 509 to communicate a phone number of a business to the coordination server 507 along with the first user's address or phone number, in response to which the coordination server 507 determines a detailed route for traveling from a starting point associated with the first user's phone number or address to the destination associated with the business, and sends detailed instructions that can be used by the client software 527 in guiding the first user to the destination.

The business computers and external severs communicates requests to pick up items via SMS messages in one embodiment, via tcp/ip and http based server side messages in another embodiment, and via other digital means in a third embodiment. These requests to pick up items are directly received by the client software, collected and displayed in one embodiment, retrieved from the server 507 in another embodiment (received via local business interface 517 for example), retrieved from external servers, such as the external business server 543 for example, in a third embodiment, or retrieved from a SMS message client in the mobile device 509 by the client software 527. Other means of retrieving and displaying requests to pick up items by the client software 527 are also contemplated. The external business server 543 or the local business interface 517 both provide services and interfaces that make it possible for external business computers and servers to deliver requests to pick up items along with recipient user identification, as well as provide services and interfaces to retrieve current location, current route, current destination or current street addresses of the users of the mobile devices, such as the user of the mobile device 509. Other types of user or service related information, relevant advertisements, coupons and product information are delivered by the business computers and servers to the client software 527 via the local business interface 517, or directly to the client software 527 (or also to an SMS client or messaging client in the mobile device 509). The client software 527 is also capable of scanning and processing received SMS or other forms of messaging received by the mobile device 509 and retrieving requests to pick up items, advertisements, coupons, etc. delivered by local businesses and organizations, etc.

In one embodiment, the client software 527 determines user is driving along a route, determines the current location or the street name, then determines business on that street or in proximity to that location, then retrieves from a list of requests to pick up items or from a task list those of the requests that are relevant to the user while the user is at that location or on the current route, and then displays it to the user. Similarly, in a related embodiment, the client software 527 retrieves the requests to pick up items from an SMS message list (maintained by an SMS client, for example) or a messaging client's local message repository or database and displays retrieved requests to pick up items (and other associated advertisements, etc.) to the user in a timely and useful fashion (such as, while the user is driving along the route, or along the street, and in proximity to those businesses).

As one of ordinary skill in the art will appreciate, the terms “task” and “task list,” as may be used herein, include work assigned to a person, things to be completed by a user that the user has planned, operations to be conducted by a user under the direction of someone else, and a collection of work to be done, a collection of things to be achieved, or a collection items to be purchased. As one of ordinary skill in the art will appreciate, the terms “todo” used herein includes work planned for completion by the user, work assigned to that user by another individual, a schedule of things to achieve or complete that is derived from a scheduler software, a planning tool, etc.

As one of ordinary skill in the art will appreciate, the terms “operably coupled” and “communicatively coupled,” as may be used herein, include direct coupling and indirect coupling via another component, element, circuit, or module where, for indirect coupling, the intervening component, element, circuit, or module does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As one of ordinary skill in the art will also appreciate, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two elements in the same manner as “operably coupled” and “communicatively coupled.”

Although the present invention has been described in terms of GPS coordinates/and navigational information communication involving mobile phones and computers, it must be clear that the present invention also applies to other types of devices including mobile devices, laptops with a browser, a hand held device such as a PDA, a television, a set-top-box, a media center at home, robots, robotic devices, vehicles capable of navigation, and a computer communicatively coupled to the network.

The present invention has also been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claimed invention.

The present invention has been described above with the aid of functional building blocks illustrating the performance of certain significant functions. The boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality. To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claimed invention.

One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.

Moreover, although described in detail for purposes of clarity and understanding by way of the aforementioned embodiments, the present invention is not limited to such embodiments. It will be obvious to one of average skill in the art that various changes and modifications may be practiced within the spirit and scope of the invention, as limited only by the scope of the appended claims. 

What is claimed is:
 1. A mobile device comprising: a processing circuitry, memory and storage; a global positioning system (GPS) receiver circuitry; a client software, that is executed by the processing circuitry, wherein the client software comprises a navigation component that interacts with the GPS receiver circuitry, the navigation component capable of navigating and providing directions to a destination to a user of the mobile device; the client software displaying a plurality of requests to pick up items received from a plurality of businesses associated with, or located on, a current route being navigated by the navigation component; the client software configured to selectively send a user provided update message regarding the corresponding ones of the plurality of requests to pick up items, to the corresponding plurality of businesses; the client software accepting a task list comprising a plurality of tasks to be completed by the user of the mobile device, based on a current location of the mobile device, a street name associated with the current location, or based on current route being navigated; wherein the client software prompts the user to mark each of the tasks in the task list as completed, skipped or deferred, and wherein the client software records and reports the corresponding task status, and wherein the client software prompts the user to respond to each of the plurality of requests to pick up items received by providing completion status.
 2. The mobile device of claim 1 wherein the requests to pick up items comprise requests to pick up one or more of medicines ordered, laundry dropped off, grocery ordered, magazines and books ordered, food ordered, mail stopped, children dropped off, packages awaiting pickup, rental equipment, electronic devices, and equipment dropped off for repairs.
 3. The mobile device of claim 1 wherein the task list comprises a plurality of tasks that are specific to the user, to be completed by the user, after the user has reached the specific destination; and the client software managing and reporting the completion status of the plurality of tasks.
 4. The mobile device of claim 1 wherein the client software accepts a task list comprising a plurality of tasks to be completed by the user of the mobile device, in response to a notification sent by the client software announcing proximity to, or arrival at the destination.
 5. The mobile device of claim 1 wherein the client software is configured to convert the plurality of requests to pick up items from a plurality of businesses into a todo list to be presented to the user, wherein the user is also subsequently prompted for completion status update for the items on the todo list.
 6. The mobile device of claim 5 wherein the todo list is assigned by the user of the mobile device to another mobile user for completion.
 7. The mobile device of claim 1 wherein the client software is configured to convert a plurality of requests to pick up items from a plurality of businesses into a todo list to be presented to users in a group comprising a plurality of members, wherein the plurality of members are also subsequently prompted for completion status update for the items on the todo list.
 8. The mobile device of claim 1 further comprising: the client software extracting the plurality of requests to pick up items from a plurality of businesses from a task list, based on a current street address or a current location of the mobile device; and the client software prompting the user of the mobile device to provide a completion status for the requests to pick up items.
 9. The mobile device of claim 1 further comprising: the client software converting the plurality of requests to pick up items from a plurality of businesses into a todo list to be presented to the user, wherein the user is also subsequently prompted for a completion status update for the items on the todo list.
 10. The mobile device of claim 1 wherein the client software displays availability status of items purchased online for in-store pickups at local businesses, based on a current street address or a current location of the mobile device.
 11. The mobile device of claim 10 wherein the requests to pick up items received from a plurality of businesses is accompanied by advertisements on related products and services.
 12. A server communicatively coupled to a first mobile device, the server comprising: at least one processor for communicating with the first mobile device, the at least one processor operable to, at least: receive a plurality of requests to pick up items, from a plurality of businesses, along with a corresponding user identification and addresses of those corresponding businesses or a reference to those corresponding businesses; receive a current location or a current street name from a client software in the first mobile device and determine a user specific set of the plurality of requests to pick up items; deliver to the client software in the first mobile device the user specific set of the plurality of requests to pick up items; deliver an update message, if any are received from the first mobile device, to the corresponding plurality of businesses, deliver to the client software of the first mobile device, based on a current location of the first mobile device, a street name associated with the current location, or based on current route being navigated, a task list comprising a plurality of tasks to be completed by the user of the first mobile device; and receive and store a task completion status for each of the plurality of tasks as they are reported by the client software of the first mobile device.
 13. The server of claim 12 wherein the task list is assembled from a plurality of tasks reported or forwarded by a plurality of authorized individuals associated with the user of the first mobile device.
 14. The server of claim 12 wherein the task list is assembled from a plurality of tasks reported or forwarded by a plurality of mobile devices being used by authorized individuals associated with the user of the first mobile device.
 15. The server of claim 12 wherein the at least one processor, upon determination of task completion for the task list, updates the status for the corresponding entries in a general pool of tasks and a user-specific pool of tasks.
 16. The server of claim 12 wherein the server receives arrival information at corresponding waypoints along a route, from a plurality of mobile devices, and, in response, communicates a set of dynamically assigned tasks to the corresponding users of the plurality of mobile devices, wherein the server subsequently receives a completion status response from the plurality of mobile devices.
 17. The server of claim 16 wherein the server receives a completion status response from the first mobile device from each of the waypoints, wherein the completion status response is associated with the current set of tasks communicated by the server to the first mobile device.
 18. The server of claim 12 wherein the server receives, from the first mobile device used by a first user, a notification indicating arrival at a destination, or proximity to the destination, and, in response, the server communicates to the first mobile device a set of tasks to be completed by the first user, wherein the set of tasks are those previously specified by a second user employing a second mobile device, wherein the set of tasks are stored at the server until delivery to the first mobile device.
 19. The server of claim 12 wherein from the first mobile device is provided a route comprising a plurality of waypoints for navigation, wherein the server receives a notification from the first mobile device whenever the first mobile device determines that it has arrived at one of the waypoints, wherein, in response to the notification received, the server communicates to the first mobile device a dynamically assembled set of tasks to be completed while at that current waypoint among the plurality of waypoints.
 20. A mobile system comprising: a plurality of mobile devices including a first mobile device and a second mobile device, each of the plurality of mobile devices configured to execute and operate employing a client software capable of sending and receiving GPS based location information, and configured to receive tasks lists for completion by a corresponding user; a coordinating server communicatively coupled to a plurality of mobile devices; the coordinating server configured to receive a plurality of item pickup requests from computers associated with a plurality of businesses for opportunistic distribution to associated ones of the plurality of mobile devices; and the client software configured to display the plurality of item pickup requests received from the plurality of businesses associated with, or located on, a current route being navigated by a navigation component of the corresponding one of the plurality of mobile devices.
 21. The mobile system of claim 20 further comprising: the first mobile device specifying tasks for execution by a second user currently using the second mobile device when the second mobile device communicates a notification indicating arrival at a specific destination; the coordinating server communicating the tasks for execution when the second user reaches the specific destination; and the coordinating server receiving a completion status response from the second mobile device as and when the second user indicates completion of an associated one of the tasks.
 22. The mobile system of claim 20 wherein the coordination server offers a service that, given an address of a user, retrieves GPS coordinates and communicates it, and wherein a user employing the first mobile device can retrieve a location information for a given phone number or email address.
 23. The mobile system of claim 20 wherein the completion status response provided by the second user employing the second mobile device comprises, for each assigned task, one of the following status: completed, skipped or deferred.
 24. The mobile system of claim 20 wherein the client software in the first mobile device communicates a phone number of a business to the coordination server along with the first user's address or phone number, in response to which the coordination server determines a detailed route for traveling from a starting point associated with the first user's phone number or address to the destination associated with the business, and sends detailed instructions that can be used by the client software in guiding the first user to the destination.
 25. The mobile system of claim 20 wherein client software in the first mobile device collects a plurality of addresses selected by the first user and then determines an optimal route through those addresses selected.
 26. The mobile system of claim 25 wherein the client software in the first mobile device sends notification to other known and registered users along the optimal route to automatically inform those corresponding registered users of the approach of the first user towards their locations and the subsequent arrival of the first user at those locations.
 27. The mobile system of claim 25 wherein a notification manager in the coordination server facilitates receiving notification from a plurality of mobile devices and forwards them to the first mobile device for display to the user, along with proximity information, approaching information, and arrival information for the plurality of mobile devices.
 28. The mobile system of claim 20 wherein the coordinating server is configured to receive a plurality of reminders from computers associated with a plurality of businesses, which the coordinating server displays on corresponding ones of the plurality of mobile devices based on their current location, wherein the plurality of reminders are each one of a medical appointment reminder, a vehicle maintenance reminder, a beauty saloon service reminder, a spa service reminder and a fitness center reminder. 